2. fedora-docs-l10n/quick-docs
3. master/pages/debug-dracut-problems
4. Search

Filters

• Untranslated strings • state:empty
• Unfinished strings • state:<translated
• Translated strings • state:>=translated
• Strings marked for edit • state:needs-editing
• Strings with suggestions • has:suggestion
• Strings with variants • has:variant
• Strings with screenshots • has:screenshot
• Strings with labels • has:label
• Strings with context • has:context
• Unfinished strings without suggestions • state:<translated AND NOT has:suggestion
• Strings with comments • has:comment
• Strings with any failing checks • has:check
• Approved strings • state:approved
• Strings waiting for review • state:translated

state:>=translated

Position and priority

• Position and priority
• Position
• Priority
• Labels
• Source string
• Target string
• String age
• Last updated
• Number of words
• Number of comments
• Number of failing checks
• Key
• String location

	Translation	Source string	Target string
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	How to debug Dracut problems	How to debug Dracut problems
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — Portuguese (Brazil)	How to debug Dracut problems	Como debugar problemas com o Dracut
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — Spanish	How to debug Dracut problems	Como depurar problemas Dracut
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	Caleb McKee; Héctor Louzao; Frank Sträter	Caleb McKee; Héctor Louzao; Frank Sträter
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	*Foreword*	*Foreword*
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — Portuguese (Brazil)	*Foreword*	*Prefácio*
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — Spanish	*Foreword*	*Prefacio*
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	If you are experiencing a problem with system initialization due to Dracut, please see the link:https://discussion.fedoraproject.org/c/ask/common-issues/82/none[common bugs] document before filing a bug. Some easy configuration tweaks that fix a wide range of issues may be listed there. If the problem you are seeing is not listed there or none of the workarounds seem to help, please consider filing a bug to help us make Fedora run better on your hardware.	If you are experiencing a problem with system initialization due to Dracut, please see the link:https://discussion.fedoraproject.org/c/ask/common-issues/82/none[common bugs] document before filing a bug. Some easy configuration tweaks that fix a wide range of issues may be listed there. If the problem you are seeing is not listed there or none of the workarounds seem to help, please consider filing a bug to help us make Fedora run better on your hardware.
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	Be prepared to include some information (logs) about your system as well. These should be complete (no snippets please), not in an archive, uncompressed, with MIME type set as text/plain.	Be prepared to include some information (logs) about your system as well. These should be complete (no snippets please), not in an archive, uncompressed, with MIME type set as text/plain.
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — Spanish	Be prepared to include some information (logs) about your system as well. These should be complete (no snippets please), not in an archive, uncompressed, with MIME type set as text/plain.	Esté preparado para incluir alguna información (registros) sobre su sistema también. Esto debería estar completo (sin fragmentos por favor), no en un archivo, descomprimido, con el tipo MIME establecido como texto plano.
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	Identifying your problem area	Identifying your problem area
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — Spanish	Identifying your problem area	Identificando su área del problema
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	Remove `rhgb` and `quiet` from the kernel command line	Remove `rhgb` and `quiet` from the kernel command line
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — Spanish	Remove `rhgb` and `quiet` from the kernel command line	Quite `rhgb` y `quiet` desde la línea de comando del kernel
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	Add `rd.shell` to the kernel command line. This will present a shell	Add `rd.shell` to the kernel command line. This will present a shell
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — Spanish	Add `rd.shell` to the kernel command line. This will present a shell	Añadir `rd.shell` a la línea de comando de kernel. Esto presentará una shell
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	in case dracut is unable to locate your root device	in case dracut is unable to locate your root device
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — Spanish	in case dracut is unable to locate your root device	en caso de que dracut es incapaz de localizar su dispositivo raíz
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	Add `rd.shell rd.debug log_buf_len=1M` to the kernel command line so	Add `rd.shell rd.debug log_buf_len=1M` to the kernel command line so
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — Spanish	Add `rd.shell rd.debug log_buf_len=1M` to the kernel command line so	Añada `rd.shell rd.debug log_buf_len=1M` a la línea de comando de kernel de modo
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	that dracut shell commands are printed as they are executed	that dracut shell commands are printed as they are executed
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — Spanish	that dracut shell commands are printed as they are executed	que los comandos de shell dracut se imprimen según se ejecutan
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	Inspect the system logs:	Inspect the system logs:
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — Spanish	Inspect the system logs:	Inspeccionar los registros del sistema:
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	# less /run/initramfs/rdsosreport.txt # journalctl -a # dmesg # less /run/initramfs/init.log	# less /run/initramfs/rdsosreport.txt # journalctl -a # dmesg # less /run/initramfs/init.log
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — Spanish	# less /run/initramfs/rdsosreport.txt # journalctl -a # dmesg # less /run/initramfs/init.log	# less /run/initramfs/rdsosreport.txt # journalctl -a # dmesg # less /run/initramfs/init.log
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	Information to include in your report	Information to include in your report
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — Spanish	Information to include in your report	Información a incluir en su informe
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	All bug reports	All bug reports
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — Spanish	All bug reports	Todos los informes de error
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	In all cases, the following should be mentioned and attached to your bug report:	In all cases, the following should be mentioned and attached to your bug report:
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — Spanish	In all cases, the following should be mentioned and attached to your bug report:	En todos los casos, se debería mencionar y adjuntar lo siguiente enb su informe de error:
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	The exact kernel command-line used. Typically from the bootloader configuration file (e.g. `/etc/grub.conf`) or from `/proc/cmdline`	The exact kernel command-line used. Typically from the bootloader configuration file (e.g. `/etc/grub.conf`) or from `/proc/cmdline`
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — Spanish	The exact kernel command-line used. Typically from the bootloader configuration file (e.g. `/etc/grub.conf`) or from `/proc/cmdline`	El kernel exacto usado en la línea de comandos. Normalmente desde el archivo de configuración del cargador de arranque (p.ej. `/etc/grub.conf`) o de `/proc/cmdline`
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	A copy of your disk partition information from `/etc/fstab`	A copy of your disk partition information from `/etc/fstab`
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — Spanish	A copy of your disk partition information from `/etc/fstab`	Una copia de la información de su partición de disco de `/etc/fstab`
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	A device listing from device-mapper. This can be obtained by running the command `dmsetup ls -- tree`	A device listing from device-mapper. This can be obtained by running the command `dmsetup ls -- tree`
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — Spanish	A device listing from device-mapper. This can be obtained by running the command `dmsetup ls -- tree`	Un lista de dispositivos de device-mapper. Esto se puede obtener ejecutando el comando `dmsetup ls -- tree`
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	A list of block device attributes including vol_id compatible mode. This can be obtained by running the commands `blkid` and `blkid -o udev`	A list of block device attributes including vol_id compatible mode. This can be obtained by running the commands `blkid` and `blkid -o udev`
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — Spanish	A list of block device attributes including vol_id compatible mode. This can be obtained by running the commands `blkid` and `blkid -o udev`	Una lista de atributos de bloque de dispositivo incluyendo vol_id en modo compatible. Esto se puede obtener ejecutando los comando `blkid` y `blkid -o udev`
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	Turn on dracut debugging (see link:#debugging-dracut[the 'debugging dracut' section]), and attach all relevant information from the boot log. This can be obtained by running the command `dmesg|grep dracut`	Turn on dracut debugging (see link:#debugging-dracut[the 'debugging dracut' section]), and attach all relevant information from the boot log. This can be obtained by running the command `dmesg|grep dracut`
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	If you use a dracut configuration file, please include `/etc/dracut.conf`	If you use a dracut configuration file, please include `/etc/dracut.conf`
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	Logical Volume Management related problems	Logical Volume Management related problems
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	As well as the information from link:#all-bug-reports[the 'all bug reports' section], include the following information:	As well as the information from link:#all-bug-reports[the 'all bug reports' section], include the following information:
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	Include physical volume information by running the command: `lvm pvdisplay`	Include physical volume information by running the command: `lvm pvdisplay`
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	Include volume group information by running the command: `lvm vgdisplay`	Include volume group information by running the command: `lvm vgdisplay`
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	Include logical volume information by running the command: `lvm lvdisplay`	Include logical volume information by running the command: `lvm lvdisplay`
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	Software RAID related problems	Software RAID related problems
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	If using software RAID disk partitions, please include the output of `/proc/mdstat`	If using software RAID disk partitions, please include the output of `/proc/mdstat`
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	Network root device related problems	Network root device related problems
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	This section details information to include when experiencing problems on a system whose root device is located on a network attached volume (e.g. iSCSI, NFS or NBD). As well as the information from link:#all-bug-reports[the 'all bug reports' section], include the following information:	This section details information to include when experiencing problems on a system whose root device is located on a network attached volume (e.g. iSCSI, NFS or NBD). As well as the information from link:#all-bug-reports[the 'all bug reports' section], include the following information:
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	Please include the output of	Please include the output of
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	Debugging dracut	Debugging dracut
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	Configure a serial console	Configure a serial console
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	Successfully debugging dracut will require some form of console logging during the system boot. This section documents configuring a serial console connection to record boot messages. To enable serial console output for both the kernel and the bootloader, follow the procedure below.	Successfully debugging dracut will require some form of console logging during the system boot. This section documents configuring a serial console connection to record boot messages. To enable serial console output for both the kernel and the bootloader, follow the procedure below.
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	Open the file `/etc/grub.conf` for editing. Below the line _timeout=5_, add the following:	Open the file `/etc/grub.conf` for editing. Below the line _timeout=5_, add the following:
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	serial --unit=0 --speed=9600 terminal --timeout=5 serial console	serial --unit=0 --speed=9600 terminal --timeout=5 serial console
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	Also in `/etc/grub.conf`, add the following boot arguments to the _kernel_ line:	Also in `/etc/grub.conf`, add the following boot arguments to the _kernel_ line:
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	console=tty0 console=ttyS0,9600	console=tty0 console=ttyS0,9600
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	When finished, `/etc/grub.conf` should look similar to the example below:	When finished, `/etc/grub.conf` should look similar to the example below:
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	default=0 timeout=5 serial --unit=0 --speed=9600 terminal --timeout=5 serial console title Fedora (2.6.29.5-191.fc11.x86_64) root (hd0,0) kernel /vmlinuz-2.6.29.5-191.fc11.x86_64 ro root=/dev/mapper/vg_uc1-lv_root console=tty0 console=ttyS0,9600 initrd /dracut-2.6.29.5-191.fc11.x86_64.img	default=0 timeout=5 serial --unit=0 --speed=9600 terminal --timeout=5 serial console title Fedora (2.6.29.5-191.fc11.x86_64) root (hd0,0) kernel /vmlinuz-2.6.29.5-191.fc11.x86_64 ro root=/dev/mapper/vg_uc1-lv_root console=tty0 console=ttyS0,9600 initrd /dracut-2.6.29.5-191.fc11.x86_64.img
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	More detailed information on how to configure the kernel for console output can be found at http://www.faqs.org/docs/Linux-HOWTO/Remote-Serial-Console-HOWTO.html#CONFIGURE-KERNEL[1].	More detailed information on how to configure the kernel for console output can be found at http://www.faqs.org/docs/Linux-HOWTO/Remote-Serial-Console-HOWTO.html#CONFIGURE-KERNEL[1].
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	Using the dracut shell	Using the dracut shell
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	Dracut offers a shell for interactive debugging in the event dracut fails to locate your root filesystem. To enable the shell:	Dracut offers a shell for interactive debugging in the event dracut fails to locate your root filesystem. To enable the shell:
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	Add the boot parameter `rd.shell` to your bootloader configuration	Add the boot parameter `rd.shell` to your bootloader configuration
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	file (e.g. `/etc/grub/conf`)	file (e.g. `/etc/grub/conf`)
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	Remove the boot arguments `rhgb` and `quiet`	Remove the boot arguments `rhgb` and `quiet`
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	A sample `/etc/grub.conf` bootloader configuration file is listed below:	A sample `/etc/grub.conf` bootloader configuration file is listed below:
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	default=0 timeout=5 serial --unit=0 --speed=9600 terminal --timeout=5 serial console title Fedora (2.6.29.5-191.fc11.x86_64) root (hd0,0) kernel /vmlinuz-2.6.29.5-191.fc11.x86_64 ro root=/dev/mapper/vg_uc1-lv_root console=tty0 rd.shell initrd /dracut-2.6.29.5-191.fc11.x86_64.img	default=0 timeout=5 serial --unit=0 --speed=9600 terminal --timeout=5 serial console title Fedora (2.6.29.5-191.fc11.x86_64) root (hd0,0) kernel /vmlinuz-2.6.29.5-191.fc11.x86_64 ro root=/dev/mapper/vg_uc1-lv_root console=tty0 rd.shell initrd /dracut-2.6.29.5-191.fc11.x86_64.img
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	If system boot fails, you will be dropped into a shell as seen in the example below:	If system boot fails, you will be dropped into a shell as seen in the example below:
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	No root device found Dropping to debug shell.	No root device found Dropping to debug shell.
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	sh: can't access tty; job control turned off #	sh: can't access tty; job control turned off #
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	Use this shell prompt to gather the information requested above (see link:#all-bug-reports[the 'all bug reports' section]).	Use this shell prompt to gather the information requested above (see link:#all-bug-reports[the 'all bug reports' section]).
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	Accessing the root volume from the dracut shell	Accessing the root volume from the dracut shell
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	From the dracut debug shell, you can manually perform the task of locating and preparing your root volume for boot. The required steps will depend on how your root volume is configured. Common scenarios include:	From the dracut debug shell, you can manually perform the task of locating and preparing your root volume for boot. The required steps will depend on how your root volume is configured. Common scenarios include:
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	A block device (e.g. `/dev/sda7`)	A block device (e.g. `/dev/sda7`)
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	A LVM logical volume (e.g. `/dev/VolGroup00/LogVol00`)	A LVM logical volume (e.g. `/dev/VolGroup00/LogVol00`)
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	An encrypted device (e.g. `/dev/mapper/luks-4d5972ea-901c-4584-bd75-1da802417d83`)	An encrypted device (e.g. `/dev/mapper/luks-4d5972ea-901c-4584-bd75-1da802417d83`)
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	A network attached device (e.g. `netroot=iscsi:@192.168.0.4::3260::iqn.2009-02.org.fedoraproject:for.all`)	A network attached device (e.g. `netroot=iscsi:@192.168.0.4::3260::iqn.2009-02.org.fedoraproject:for.all`)
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	The exact method for locating and preparing will vary. However, to continue with a successful boot, the objective is to locate your root volume and create a symlink `/dev/root` which points to the file system. For example, the following example demonstrates accessing and booting a root volume that is an encrypted LVM Logical volume.	The exact method for locating and preparing will vary. However, to continue with a successful boot, the objective is to locate your root volume and create a symlink `/dev/root` which points to the file system. For example, the following example demonstrates accessing and booting a root volume that is an encrypted LVM Logical volume.
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	Inspect your partitions using `parted`:	Inspect your partitions using `parted`:
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	# parted /dev/sda -s p Model: ATA HTS541060G9AT00 (scsi) Disk /dev/sda: 60.0GB Sector size (logical/physical): 512B/512B Partition Table: msdos	# parted /dev/sda -s p Model: ATA HTS541060G9AT00 (scsi) Disk /dev/sda: 60.0GB Sector size (logical/physical): 512B/512B Partition Table: msdos
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	Number Start End Size Type File system Flags 1 32.3kB 10.8GB 107MB primary ext4 boot 2 10.8GB 55.6GB 44.7GB logical lvm	Number Start End Size Type File system Flags 1 32.3kB 10.8GB 107MB primary ext4 boot 2 10.8GB 55.6GB 44.7GB logical lvm
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	You recall that your root volume was a LVM logical volume. Scan and	You recall that your root volume was a LVM logical volume. Scan and
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	activate any logical volumes:	activate any logical volumes:
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	# lvm vgscan # lvm vgchange -ay	# lvm vgscan # lvm vgchange -ay
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	You should see any logical volumes now using the command `blkid`:	You should see any logical volumes now using the command `blkid`:
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	# blkid /dev/sda1: UUID="3de247f3-5de4-4a44-afc5-1fe179750cf7" TYPE="ext4" /dev/sda2: UUID="Ek4dQw-cOtq-5MJu-OGRF-xz5k-O2l8-wdDj0I" TYPE="LVM2_member" /dev/mapper/linux-root: UUID="def0269e-424b-4752-acf3-1077bf96ad2c" TYPE="crypto_LUKS" /dev/mapper/linux-home: UUID="c69127c1-f153-4ea2-b58e-4cbfa9257c5e" TYPE="ext3" /dev/mapper/linux-swap: UUID="47b4d329-975c-4c08-b218-f9c9bf3635f1" TYPE="swap"	# blkid /dev/sda1: UUID="3de247f3-5de4-4a44-afc5-1fe179750cf7" TYPE="ext4" /dev/sda2: UUID="Ek4dQw-cOtq-5MJu-OGRF-xz5k-O2l8-wdDj0I" TYPE="LVM2_member" /dev/mapper/linux-root: UUID="def0269e-424b-4752-acf3-1077bf96ad2c" TYPE="crypto_LUKS" /dev/mapper/linux-home: UUID="c69127c1-f153-4ea2-b58e-4cbfa9257c5e" TYPE="ext3" /dev/mapper/linux-swap: UUID="47b4d329-975c-4c08-b218-f9c9bf3635f1" TYPE="swap"
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	From the output above, you recall that your root volume exists on an encrypted block device. Unlock your encrypted root volume.	From the output above, you recall that your root volume exists on an encrypted block device. Unlock your encrypted root volume.
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	UUID=$(cryptsetup luksUUID /dev/mapper/linux-root) cryptsetup luksOpen /dev/mapper/linux-root luks-$UUID Enter passphrase for /dev/mapper/linux-root: Key slot 0 unlocked.	UUID=$(cryptsetup luksUUID /dev/mapper/linux-root) cryptsetup luksOpen /dev/mapper/linux-root luks-$UUID Enter passphrase for /dev/mapper/linux-root: Key slot 0 unlocked.
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	Next, make a symbolic link to the unlocked root volume	Next, make a symbolic link to the unlocked root volume
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	ln -s /dev/mapper/luks-$UUID /dev/root	ln -s /dev/mapper/luks-$UUID /dev/root
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	With the root volume available, you may continue booting the system by exiting the dracut shell	With the root volume available, you may continue booting the system by exiting the dracut shell
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	exit	exit
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	Summary of dracut kernel command line options	Summary of dracut kernel command line options
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	A selection of the most common debugging related dracut options:	A selection of the most common debugging related dracut options:
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	`*rd.shell*`	`*rd.shell*`
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	Drop to a shell, if the initramfs fails.	Drop to a shell, if the initramfs fails.
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	`*rd.debug*`	`*rd.debug*`
	fedora-docs-l10n/quick-docs/master/pages/debug-dracut-problems — English	Set -x for the dracut shell.	Set -x for the dracut shell.

• 1 / 2
  / 2